Improve descriptions for X/Y schemas#261474
Conversation
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
| { | ||
| meta: { | ||
| description: | ||
| 'Dependent axis (metric): the measured values. Always use y for metrics regardless of chart orientation — chart orientation is controlled by the type field (e.g. bar vs bar_horizontal), not by swapping x and y.', |
There was a problem hiding this comment.
hmm, let's check if that works, but I feel like this is a lot of tokens with a description this long. I wonder if only adding "range" and "domain" wouldn't be good enough 😅 I'll try to check tomorrow!
There was a problem hiding this comment.
I wasn't even considering token length here, just asked to produce and validate a good description that was non ambigious for an LLM.
I would really not recommend changing the description to reduce the number of tokens just for that, this is not something we evaluate and control. If we need this level of optimization probably we should create a "llm_description" meta that is minimal and just works for LLMs
There was a problem hiding this comment.
Ok, I just checked and unfortunately this description doesn't affect the agent action at all 🫠 I tried to tweak it, but looks like nothing works and we have to do it at agent level. Please feel free to merge this, we'll fix it on our end.
4 participants
Summary
Improved descriptions for the X and Y properties to avoid LLM confusing X and Y when handling charts oriented in a different way.
fix #260632